Visualizations of multi-nodal transfers and gesture-based interactivity in virtual or augmented reality

ABSTRACT

Disclosed is an approach for generating interactive visualizations for multi-nodal transfers that may involve terminal nodes and multiple transitional nodes by using various protocols to acquire data from computing systems or devices associated with each node. A first visualization layer comprising a set of geographic or physical indicators in a multi-nodal transfer route (which comprises a set of three or more nodes) may be generated. API protocols (and/or non-API protocols) corresponding to each node in the transfer route may be identified. The protocols may be executed to obtain, from computing systems and devices associated with the nodes, data packets used to generate a second visualization layer, which may comprise graphics that visually depict details of a transfer along the transfer route. An overlay of visualization layers may be displayed such that the graphics are displayed in association with multiple nodes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/119,700 filed Dec. 11, 2020, the entirety of which is incorporatedherein by reference.

TECHNICAL FIELD

Embodiments and aspects of the innovation relate to renderingvisualizations of multi-nodal transfers and interactivity with thevisualizations.

BACKGROUND

Multi-destination transfers of goods and funds are becoming moreprevalent, including transfers across international borders. In theprocess of the transfer, the items may make multiple stops along a routefrom a source to a destination. For example, goods may begin by leavingon a truck from the sending entity, have a first stop or transfer at ashipping yard, a second stop or transfer at a second shipping yard, anda third stop or transfer to another trucking entity before actuallyreaching the destination. In another example, funds transferredinternationally via, for example, wire transfer may include multipleintermediary destinations. Use of intermediary enterprises introducesuncertainties, as products or funds may become untraceable for certainperiods of time, may be delayed, or may simply go missing with littleexplanation.

SUMMARY

Various embodiments relate to a computer-implemented method comprising:generating a first visualization layer comprising a set of geographic orphysical indicators in a multi-nodal transfer route comprising a set ofthree or more nodes that include terminal nodes and at least onetransitional node; identifying a first computing application programinterface (API) protocol corresponding to a first node in the transferroute, and a second API protocol corresponding to a second node in thetransfer route; executing the first API protocol to obtain, from a firstcomputing system, a first data packet corresponding to the first node,and executing the second API protocol to obtain, from a second computingsystem, a second data packet corresponding to the second node;generating a second visualization layer comprising, (i) based on thefirst data packet, a first graphic visually depicting a first detail ofa transfer of an item along the transfer route and, (ii) based on thesecond data packet, a second graphic visually depicting a second detailof the transfer of the item along the transfer route; and displaying anoverlay of the first visualization layer with the second visualizationlayer such that the first graphic and the second graphic are displayedin association with at least two nodes in the set of nodes.

Various embodiments relate to a system including a processor and amemory storing instructions thereon. The instructions, when executed bythe processor, cause operations including generate a first visualizationlayer comprising a set of geographic or physical destinations in aroute, the set of destinations comprising a first node, a second node,and a third node, identify a first computing application programinterface (API) protocol corresponding with the first node, and a secondAPI protocol corresponding with the second node, execute the first APIprotocol to obtain, from a first computing system, a first status of atransfer and executing the second API protocol to obtain, from a secondcomputing system, a second status of the transfer, generate a secondvisualization layer comprising a first graphic corresponding with thefirst status and a second graphic corresponding with a second status,and provide a graphical user interface (GUI) comprising an overlay ofthe first visualization layer with the second visualization layer suchthat at least two nodes in the set of destinations are displayed inassociation with the first and second graphics.

This summary is illustrative only and is not intended to be in any waylimiting. Other aspects, inventive features, and advantages of thedevices or processes described herein will become apparent in thedetailed description set forth herein, taken in conjunction with theaccompanying figures, wherein like reference numerals refer to likeelements.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of an international transfer system, accordingto various potential embodiments.

FIG. 2 is a flow diagram of a method of providing a visual display of amulti-destination transfer, according to various potential embodiments.

FIG. 3 is an example of a first visualization layer, according tovarious potential embodiments.

FIG. 4 is an example of a rendered visualization of a multi-destinationtransfer, according to various potential embodiments.

FIG. 5 is a second example of a rendered visualization of amulti-destination transfer, according to various potential embodiments.

FIG. 6 is an example of an updated visualization of a multi-destinationtransfer based on a user input, according to various potentialembodiments.

FIG. 7 is a flow diagram of a method of generating and updating amulti-nodal transfer, according to various potential embodiments.

FIG. 8 depicts a multi-layered visualization for a user, according tovarious potential embodiments.

FIG. 9 depicts multiple visualizations as the visualization is updatedwith additional information over time, according to various potentialembodiments.

DETAILED DESCRIPTION

Systems, apparatuses, and methods for rendering and providing enhancedvisualizations of multi-nodal transfers according to various embodimentsare disclosed herein. A computing system of a service provider or otherenterprise that is facilitating or otherwise involved in a multi-nodaltransfer may render or generate a visualization of a set of geographicor physical destinations along a transfer route and present thevisualization to a display, for example, on a user device. Thevisualization is interactive such that a user of the user device caninteract with the visualization in order to obtain information regardingthe transfer. For example, responsive to a user input, the enterprisecomputing system determines whether additional information is needed,determines how to access or retrieve the additional information from oneor more external computing systems, and updates one or more layers ofthe visualization to enhance interactivity among the user, enterprisecomputing system, and the external computing systems. As used herein, a“transfer” is advancement or movement of funds or goods that involvesterminal nodes (associated with, e.g., a source computing system and adestination computing system) and various transitional nodes (associatedwith, e.g., various intermediary computing systems). In variousembodiments, computing systems in multi-nodal transfers lack data orvisibility on other nodes and computing systems involved in thetransfers. Similarly, a user may additionally lack any information on atransfer after it has been initiated by a terminal computing systemand/or until after it has been received at another terminal computingsystem (e.g., information on transitional nodes available tointermediary computing systems).

In various embodiments, the disclosed approach obviates obfuscation viavarious computing processes that are configured to acquireparticularized data and render graphical depictions of that data ininteractive visualizations. Moreover, the computing system may generateand update multi-layered visualizations that are responsive to one ormore user inputs. As such, the computer systems and methods describedherein provide an improved ability for the various computing systems tointeract with one another and for the enterprise computing system tointeract with clients/users. The enterprise computing system uniquelyacquire and characterize data on transitional nodes via applicationprogramming interface (API) protocols, generate multi-layeredvisualizations, and display overlays of layers on, for example,augmented reality (AR) or virtual reality (VR) devices. The enterprisecomputing system may dynamically determine a computing source for thatinformation, execute one or more protocols to retrieve the informationfrom the computing source, and update the visualization in aninteractive manner. Beneficially, the enterprise computing systemimproves the ability of the computing system to interact with usersbased on dynamic management of information retrieved from one or moreterminal and/or intermediary computing systems.

Referring now to FIG. 1 , a block diagram of an international transfersystem 100 is shown according to an example embodiment. The system 100includes a user device 101 associated with a client/user, an enterprisecomputing system 102 associated with an enterprise institution, andmultiple intermediary computing systems 103 a-c (e.g., computing devicesof multiple intermediary enterprises that are leveraged as part of amulti-destination transfer) that are configured to communicate over anetwork 106. The user device 101 is owned by or otherwise associatedwith a client/user. The user may be an individual, businessrepresentative, large and small business owner, and so on. The user orclient may be an existing or a new client to the enterprise associatedwith the enterprise computing system 102. As described above, theenterprise computing system may be a financial institution computingsystem, department store computing system, government departmentcomputing system, or other type of computing system that facilitatesmulti-nodal transfers. In the example shown, the enterprise computingsystem is a financial institution computing system that is able totransfer monetary contents to a destination enterprise computing system.That is, in the example shown, the financial institution computingsystem may initiate a multi-nodal transfer. In other configurations, theenterprise computing system may be an independent platform that providesa service of monitoring multi-nodal transfers from an initiatingenterprise computing system to a destination enterprise computingsystem. In some embodiments, the transfer may be an international moneytransfer, international wire transfer, or an international transfer ofgoods. The present disclosure is applicable with each configuration.

The intermediary computing systems 103 a-d are computing systemsassociated with respective geographic or physical destinations in aroute of the transfer. The intermediary computing systems 103 a-d mayinclude one or more computing devices or systems that are configured tointeract and communicate with the enterprise computing system 102 viathe network 106. For example, intermediary computing systems 103 a-dvarious server systems, computers, or other computing devices thatinclude an API that allows for the communication of data with theenterprise computing system 102 over the network. For example, once theenterprise computing system 102 determines that a particularintermediary computing system is involved with a transfer, theenterprise computing system 102 may execute an API protocol to requestfor a first status of the transfer from the respective intermediarycomputing system 103 a. In return, the intermediary computing system 103a is configured to obtain information for the first status and transmitthe first status to the enterprise computing system 102. In the exampleof the transfer being an international monetary transfer, the firststatus may include information regarding the entity that theintermediary computing system received the transfer from (e.g., sendingentity information), information regarding the entity that theintermediary computing system is sending or sent the transfer to (e.g.,receiving entity information), the currency and amount received from thesending entity, the currency and amount sending to the receiving entity,an identification of the agent or employee associated with the transferat the sending entity, an identification of the agent or employeeassociated with the transfer at the intermediary computing system,and/or an identification of the agent or employee associated with thetransfer at the receiving entity.

The user device 101 is configured to interact with a user such that theclient may conveniently and efficiently interact with the visualizationof the transfer. The user device 101 is shown to include processingcircuitry 119 (also referred to as a processing circuit) including aprocessor 110 and a memory 111, a display 112, and a network interface114. It should be appreciated that the user device may also includeother elements as well, such as a vibrate-able element, a speaker, etc.The user device 101 is structured to and configured to enable the userto access the network 106 (e.g., to send and receive information/dataover the network). Examples of the user device 101 include a mobilephone such as a smartphone, a tablet, a wearable computing device (e.g.,an augmented reality eye ware device), a laptop etc. Wearable computingdevices refer to any type of device that an individual wears including,but not limited to, a watch (e.g., a smart watch), glasses (e.g., eyeglasses, sunglasses, smart glasses, virtual reality (VR) glasses,augmented reality (AR) glasses etc.), bracelet (e.g., a smart bracelet),etc. In some embodiments, the user device 101 includes one or moresensors 117 that allow for user inputs via the user device 101. The oneor more sensors 117 may include various cameras, detectors, lightsources, and or other electronic equipment configured to capture one ormore user inputs. In some embodiments, the one or more sensors 117include an eye tracking system, a gesture or proximity sensing system, adepth sensing system, a touch screen, and/or a combination thereof.

The user device 101 may include program logic (e.g., instructions)stored by the memory 111 and executable by the processor 110 toimplement at least some of the functions described herein. The processor110 may be implemented as an application specific integrated circuit(ASIC), one or more field programmable gate arrays (FPGAs), a digitalsignal processor (DSP), a group of processing components, or othersuitable electronic processing components. The memory device 111 (e.g.,RAM, NVRAM, ROM, Flash Memory, hard disk storage, etc.) may store dataand/or computer code for facilitating the various processes describedherein. Accordingly, the memory device 111 may be or include tangible,non-transient volatile memory or non-volatile memory. The memory devicemay include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described herein.

As shown, the user device 101 includes an enterprise client application151. The enterprise client application 151 is coupled to the enterprisecomputing system 102 such that information may be exchanged between theenterprise computing system 102 and the client application 151. In oneembodiment, the enterprise client application 151 is hard coded into thememory 111. In another embodiment, the processor 110 may be configuredto download the client application 151. For example, a developer maymake or create the client application 151 to be downloaded (e.g., via anapp store, or in another manner). Responsive to a selection of anappropriate link, the enterprise client application 151 can betransmitted to the user device 101 and cause itself to be installed onthe user device 101. Installation of the enterprise client application151 allows the client application 151 to be executable by the processor110. Examples of downloadable enterprise client applications 151 includea mobile banking application, a mobile wallet application, and so on.The client application 151 may be a thin or a thick application. Ineither situation, the execution of the application (either thick, thin,or smart client application) may enable the user to access one or moreaccounts of the client (e.g., provided and maintained by the enterprisecomputing system). Accordingly, execution of the application allowsfunctions associated with that application. In the example shown, theenterprise client application 151 is a mobile banking application thatenables a user to view, access, and manage accounts administered by theenterprise institution computing system (e.g., checking and/or savingsaccount, mortgage account, brokerage account, and so on) or view ormanage transfers of the user as described herein.

The network interface 114 may include one or more antennas ortransceivers and associated communications hardware and logic. Thenetwork interface 114 is structured to allow the user device 101 toaccess and couple/connect to the network 106 to, in turn, exchangeinformation with for example the enterprise computing system 102. Thatis, the network interface 114 is coupled to the processor 110 and memory111 and configured to enable a coupling to the network 106. The networkinterface 114 allows for the user device 101 to transmit and receiveinternet data and telecommunication data. Accordingly, the networkinterface 114 includes any one or more of a cellular transceiver (e.g.,CDMA, GSM, LTE, etc.), a wireless network transceiver (e.g., 802.11X,ZigBee, WI-FI, Internet, etc.), and a combination thereof (e.g., both acellular transceiver). Thus, the network interface 114 enablesconnectivity to WAN as well as LAN (e.g., Bluetooth, NFC, etc.transceivers). Further, in some embodiments, the network interface 114includes cryptography capabilities to establish a secure or relativelysecure communication session between other systems such as theenterprise computing system 102, a second user device, the intermediarycomputing systems 103 a-d, and/or any third-party computing system. Inthis regard, information (e.g., account information, transferinformation, visualizations of the transfer information, financial data,and/or other types of data) may be encrypted and transmitted to preventor substantially prevent a threat of hacking.

It should be understood that the user device 101 may include otherstructures with associated functionality as well. For example, the userdevice 101 and/or client application 151 may include locationdetermination logic. The location determination logic determines thelocation of the user device 101 (e.g., for use by the client application151). A user may opt-in to using the location determination logic toprovide enhanced protection against fraudulent transactions, asdescribed below. The location determination logic may use a satellite(GPS) sensor or cellular towers to determine the location coordinates ofthe user device 101 include a global positioning system (GPS) structuredto at least one of determine or receive data indicative of thegeolocation of the user device 101. This “location data” may provide anindication of a location of the user device 101.

The network 106 provides communicable coupling between the components ofFIG. 1 . The network 106 may include one or more of a local areanetwork, a wide area, a wired network, and/or a combination of wirelessand wired networks. Examples of network configurations include theInternet, a cellular network, Wi-Fi, Wi-Max, a proprietary bankingnetwork, etc. In some embodiments, the network 106 includes aproprietary banking network to provide secure or substantially securecommunications. The network 106 is structured to permit the exchange ofdata, values, instructions, messages, and the like between and amongvarious components of FIG. 1 .

The enterprise computing system 102 is associated with an enterprise orprovider institution. As mentioned above, in the example shown, theenterprise institution is a financial institution that is configured toretrieve information regarding a transfer from the user device 101 andthe intermediary computing devices 103 a-d. As shown, the enterpriseinstitution computing system 102 is structured as one or more backendprocessing components, such as servers. The enterprise institutioncomputing system 102 includes processing circuitry 120 including amemory device 123, and a network interface 124. The network interface124 is structured to enable the enterprise computing system 102 tocouple or connect to and to exchange information over the network 106with, for example, the user device 101. The network interface 124 may becoupled to the processing circuitry 120 in order to enable theprocessing circuitry 120 to receiving and transmit messages, data, andinformation via the network 106.

The processing circuitry 120 is shown to include rendering logic 121,application programming interface (API) logic 122, and a memory 123. Insome embodiments, the processing circuitry 120 may include one or moreprocessors that are configured to communicate such that the processingcircuitry 120 may perform or assist in performing any of the operations,steps, or methods discussed herein. The rendering logic 121 may benon-transitory machine-readable instructions stored thereon that whenaccessed and executed by the processor, cause the processor to perform,execute, or assist in executing any of the operations, steps, or methodsdiscussed herein, for example, in regard to the generation of theinteractive visualizations. As an example, the rendering logic 121 mayinclude an executable program or application that has rules, particularprocedures, or other logic therein that, when executed by the processor,enable the enterprise computing system 102 to perform or assist inperforming the operations and methods regarding generating and providingthe interactive visualizations discussed herein. The API logic 122 maybe non-transitory machine-readable instructions stored thereon that whenaccessed and executed by the processor, cause the processor to perform,execute, or assist in executing any of the operations, steps, or methodsdiscussed herein, for example, in regard to the determination of theintermediary computing systems 103 a-d involved in a particular transferand their associated API protocols.

The memory 123 may one or more tangible, non-transient volatile memoryor non-volatile memory devices configured to digitally storeinformation. In the example shown, the memory 123 includes anintermediary database 125 and a client database 126. The intermediarydatabase 125 and the client database 126 are structured as repositoriesfor information. In this regard, the client database 126 is configuredto store, hold, and maintain information for a plurality of clients ofthe enterprise. For example, the client database 126 may storeinformation such as client information (e.g., names, addresses, phonenumbers, and so on), information regarding the user device 101 (e.g.,mobile service identification number (MSIN), internet protocol (IP)address, etc.), or other information. The intermediary database 125 isconfigured to store, hold, and maintain information regarding theintermediary computing systems. For example, the intermediary database125 is configured to store information regarding API protocols for eachof the enterprise computing systems, the geographic location of eachenterprise computing system, and/or network information such as IPaddresses for each enterprise computing system. In this way, forexample, the enterprise computing system 102 is able to use theinformation stored in the intermediary database 125 in order tocommunicate with each of the intermediary computing systems 103 a-d. Theintermediary database 125 is also configured to store historicalinformation for each of the intermediary enterprises and/or agentsthereof. For example, the intermediary database 125 may store historicalinformation regarding the amount of time that respective intermediariestook to complete a transfer, information regarding the amount of timethat a transfer took when a particular agents at the intermediary wasassociated with a transfer, information regarding transfers that therespective intermediaries failed to complete, etc. In this way, forexample, the enterprise computing system 102 is able to access thishistorical information and employ artificial intelligence (AI) in orderto provide a user with an estimated time for the transfer to completeand/or a probability of a successful completion of the transfer based onthe intermediary computing systems involved in a transfer.

Referring now to FIG. 2 , a flow diagram of a method 200 providing avisual display of a multi-destination transfer is shown according to anexample embodiment. Because method 200 may be implemented using thecomponents of FIG. 1 , reference may be made to one or more componentsto aid explanation of method 200. Generally, method 200 relates tovarious processes implemented in order to provide a visualization of amulti-destination transfer to a user.

At process 201, a first visualization layer including a set ofgeographic or physical destinations in a route of a transfer isgenerated. The first visualization layer includes a first node, a secondnode, and a third node, each of the nodes corresponding to one of theset of geographic or physical destinations. For example, the first nodemay be a first terminal node corresponding to a first (terminal)enterprise computing system that initiates the transfer, the second nodemay be a transitional node corresponding to a first (transitional)intermediary computing system that receives the transfer from the firstenterprise computing system and sends the transfer to a destinationenterprise computing system corresponding to the third node (a secondterminal node). Alternatively or additionally, the first visualizationlayer may include additional or fewer nodes each corresponding with anenterprise computing system of the set of geographic or physicaldestinations. For example, depending on the context of the transfer, thetransfer may include additional intermediary computing systems.

In an embodiments, the enterprise computing system 102 generates thefirst visualization layer. The enterprise computing system 102 may bethe same enterprise computing system associated with the first node. Forexample, in some embodiments as indicated above, the enterprisecomputing system 102 may be the enterprise computing system that isinitiating the transfer. In this example, the enterprise computingsystem 102 receives a request from a user to initiate a transfer to adestination enterprise computing system. The enterprise computing system102 may determine a route including one or more intermediary computingsystems that need to be included on the route in order for the transferto reach the destination enterprise computing system and begin thetransfer by sending the transfer to a first of the intermediarycomputing systems.

In alternative embodiments, the enterprise computing system 102 may notbe the enterprise computing system associated with the first node. Forexample, as indicated above, the enterprise computing system 102 may bea third party computing system that receives information regarding atransfer initiated at a first enterprise computing system. Theinformation regarding the transfer may be received from a computingsystem of the first enterprise (e.g., a first intermediary enterprise103 a) and/or from the user device 101. That is, in a first example, theenterprise computing system 102 may be configured to provide avisualization service to the first enterprise computing system and, inresponse to the first enterprise computing system initiating a transfer,the first enterprise may transmit information regarding the initiatedtransfer to the enterprise computing system 102 that notifies theenterprise computing system that the transfer has begun. In thisexample, the information regarding the initiated transfer may include atransfer amount, the currency of the initiated transfer, a currency thatthe transfer should be received in, and/or information regarding theintermediary computing systems that will be involved in the transfer.Further in this example, the enterprise computing system 102 maydetermine the set of geographic or physical destinations in the routebased on the information received from the first enterprise computingsystem. In a second example, a user may access the enterpriseapplication 151 on the user device 101, enter in information regarding atransfer initiated at a first enterprise computing system that the userrequested, and request the enterprise computing system 102 to generate avisualization of the transfer. In this example, in response to receivingthe request, the enterprise computing system 102 may determine theinitiating computing system, the intermediary computing systems, and thedestination computing system either based on information in the requestor dynamically through various API calls in order to determine the setof geographic or physical destinations in the route.

At process 202, a first API protocol corresponding with the first nodeis identified and a second API protocol corresponding with the secondnode is identified. For example, the enterprise computing system 102determines a first computing system associated with the first node basedon information regarding the transfer. The enterprise computing system102 may then cross-reference the first computing system within the APIdatabase 125 in order to determine a first API protocol that enables theenterprise computing system 102 to retrieve information from the secondcomputing system. Similarly, the enterprise computing system 102determines a second computing system that is associated with the secondnode. The enterprise computing system 102 may cross-reference the secondcomputing system within the API database 125 in order to determine asecond API protocol that enables the enterprise computing system 102 toretrieve information from the second computing system.

Additionally or alternatively, in the example where the enterprisecomputing system 102 is involved in the transfer as either theinitiating computing system (e.g., the first enterprise computingsystem), an intermediary computing system, or the destination computingsystem, the third node may correspond to the enterprise computing system102 and an API protocol for the third node is not identified. Rather,the enterprise computing system 102 may leverage information stored orreceived as part of the transfer in order to determine a third status ofthe transfer, where the third status of the transfer is associated withthe third node (e.g., the enterprise computing system 102). However, inthe example where the enterprise computing system 102 is not involved inthe transfer (e.g., is a third party to the transfer process), theenterprise computing system 102 may also identify a third API protocolcorresponding to the third node that enables the enterprise computingsystem 102 to retrieve information from a third computing system (e.g.,a third intermediary computing system 103 c) corresponding to the thirdnode. Additionally or alternatively, the enterprise computing system 102may determine API protocols corresponding to additional nodes dependingon the particular context of the transfer.

At process 203, the first API protocol is executed to obtain a firststatus of the transfer from the computing system associated with thefirst node and the second API protocol is executed to obtain a secondstatus of the transfer from the computing system associated with thesecond node. Each API protocol corresponding to a computing system maycomprise an API specific to the computing system, and one or morespecifications on using the specific API to make API calls or APIrequests to that computing system. The specifications may identify, forexample, how a request is to be formatted (e.g., how the requested datais to be identified), how the computing system making the API requestidentifies and verifies its identity (e.g., authenticates itself usingpermanent, temporary, or single-use passcodes, authentication tokens,etc.), timing of API requests, how other relevant user devices orcomputing systems are identified, and/or other information required inmaking a proper, suitable, or acceptable API request. In variousembodiments, other protocols may be used in addition to API protocols,such as requesting sensor readings, imagery, video, sound, GPScoordinates from GPS devices, RFID, wireless communications (e.g.,near-field communications (NFC), W-Fi, “Bluetooth”) etc., from deviceslocated at the various nodes. For example, a first protocol may involverequesting data from first and second devices at a first node, andperforming specific analyses on the data to generate information on anitem being transferred. For example, an API protocol may be implementedby the enterprise computing system for a first node, and a secondprotocol (e.g., using GPS coordinates corroborated by, e.g., imageanalysis for visual confirmation or wireless detection of acommunications device or tag on an item at a node, or detection of itsmovement away or toward a node) may be implemented for a second node.

At process 204, a second visualization layer is generated that includesa first graphic corresponding with the first status, a second graphiccorresponding with the second status. In some embodiments, in theexample where the enterprise computing system 102 is also involved withthe transfer, the enterprise computing system 102 may generate a thirdgraphic corresponding to the third status of the transfer, where theinformation in the third status was accessed or retrieved locally at theenterprise computing system 102. Alternatively or additionally, in theexample where the enterprise computing system 102 is not involved in thetransfer process, a third graphic corresponding to a third statusobtained from executing the third API protocol may also be generated. Insome embodiments, the number of statuses of the transfer obtained andcorresponding graphics that are generated are dependent upon the contextof the transfer and the number of destinations included with the set ofgeographic or physical destinations in the route of the transfer.

At process 205, an overlay of the first visualization layer with thesecond visualization layer is displayed such that at least two nodes inthe set of destinations are displayed such that at least two nodes inthe set of destinations are displayed in association with the first andsecond graphics. For example, in an embodiment, the enterprise computingsystem 102 may provide the first visualization layer and the secondvisualization layer to the user device 101 that is configured to displayan overlay of the first and second visualization layers. In someembodiments, the enterprise computing system 102 is configured torender/generate the overlay of the first and second visualization layersin a single graphical user interface (GUI) and provide the GUI to theuser device 101 to display. That is, in various embodiments, the userdevice 101 may be configured to perform various processes to render theoverlaid visualization to the user. In some embodiments, the enterprisecomputing system 102 renders the overlaid visualization and transmitsthe information regarding the visualization to the user device 101 thatthen displays the rendered visualization. The visualization isconfigured to graphically depict to the user the current status of thetransfer including the intermediary (e.g., the node) that is currentlyin possession of the transfer.

Moreover, as discussed in further detail below, the visualization, inparticular, the second visualization layer may include additionalinformation that is determined using AI or estimation made by theenterprise computing system 102. For example, the enterprise computingsystem 102 may access historical information regarding the enterprisecomputing systems associated with each of the nodes in order todetermine or estimate a time that the transfer will be completed by. Forexample, the first status may indicate that the first node received thetransfer at a first time and the transfer to the second node has not yetoccurred. The enterprise computing system 102 may access the historicalinformation regarding a first computing system of the first node andcalculate an average amount of time that the computing system usuallytakes in processing the transfer to a second computing system of thesecond node. Moreover, the enterprise computing system 102 may accessthe historical information regarding the second computing system of thesecond node to determine an average amount of time that the secondcomputing system of the second node usually takes to process thetransfer to a third computing system associated with the third node. Theenterprise computing system 102 may then generate another graphicalrepresentation of an estimated transfer completion date or time for thesecond visualization layer. In other embodiments, the enterprisecomputing system 102 may also generate, based on the historicalinformation, a probability score indicative of the likely success orfailure of the transfer and/or other estimations using AI or machinelearning. The enterprise computing system 102 may then store theobtained statuses within the API database in order to continue buildingthe historical information data base for future estimations.

The enterprise computing system 102 may also be configured to access thehistorical information in order to calculate a probability of how longthe transaction should that and a probability score of the chance thatthe transfer will be successful. For example, the enterprise computingsystem 102 may be configured to implement a machine learning algorithmusing the historical data points of past transfers in the database. Themachine learning algorithm may compare similar transactions to thepresent transaction and search for any abnormalities (e.g.,inconsistencies) therebetween. Moreover, the machine learning algorithmmay calculate a risk score for particular intermediary computing systemsor individuals based on similar previous transactions. For example, themachine learning algorithm may flag to the user that a particular nodeor enterprise computing system with the node has a 50% chance ofsuccessfully completing the transfer based on similar transactions notbeing completed half of the times attempted. A node having a lowprobability score of success (e.g., has a history of not completingtransfers) may be holographically or otherwise visually displayed on theuser device as part of the rendered visualization (e.g., the secondvisualization layer) to identify the node presenting the issue (e.g.,delay).

The enterprise computing system 102 may also provide on the secondvisualization layer a real-time market update (e.g., a display of realtime currency trade ratios) such that the user is able to make thetransfer that includes the exchange rates at the best value for theuser. In various embodiments, the enterprise computing system 102 mayemploy machine learning based on monitored market data to providesuggestions to the user of when the best time to initiate the transferis. For example, the machine learning algorithm may monitor thehistorical price fluctuations between the U.S. Dollar and the Euro todetermine that at noon central daylight time is the best time to make atransfer to a person or entity in the Eurozone. More particularly, themachine learning algorithm may calculate based on detected patternsbetween the U.S. Dollar and the Euro and the amount of the transfer,that the user could save a certain amount of funds (e.g., $15) byinitiating the transfer at a particular time as opposed to immediately.In some embodiments, the machine learning algorithm may accessinformation regarding past transfers of the user and provide a learninggraphic to the user (e.g., via the second visualization layer or a thirdvisualization layer) that indicates to the user that funds could havebeen saved or more value could have been transferred had the userselected to initiate the transfer at particular times of the day ormonth. In this way, the learning graphic may be referenced by the userin order to allow the user to determine the best time to initiatetransfers in the future.

In another example, the visualization including the first and secondvisualization layers may include information regarding multipletransfers. For example, a user may have multiple international transferspending at one time. The first visualization layer may include a first,second, and third node corresponding to a first of the multipletransfers and a fourth, fifth, and sixth node corresponding to a secondof the multiple transfers. The visualization generated or rendered bythe enterprise computing system 102 may include connectors between eachof the nodes with corresponding graphical representations of therespective statuses for each the first and second transfers. In thisway, the enterprise computing system 102 is able to provide a completevisualization to the user of the progress or status of their multipletransfers. If one or more of the transfers has a probability score of asuccessful completion below a threshold (e.g., 70%), then the secondvisualization layer may include a graphical representation of a warningthat is configured to indicate to the user that the particular transferis high risk. Accordingly, the user may be able to interact with thevisualization to identify the particular node that is high risk in orderto attempt to avoid that node in future transactions.

Referring now to FIG. 3 , an example of a first visualization layer 300is shown, according to an exemplary embodiment. The first visualizationlayer 300 includes set of geographic or physical destinations along aroute of a transfer. The set of geographic or physical destinationsinclude a first node 301, a second node 302, a third node 303, a fourthnode 304, a fifth node 305, a sixth node 306, and a seventh node 307visually rendered on a geographic map. The nodes 301-307 each representa respective destination along a route on which a particular transferwill travel. For example, the first node 301 (a first terminal node)represents the initiating computing system (a first terminal computingsystem), the second through sixth nodes 302-306 (transitional nodes)represent intermediary or transitional computing systems, and theseventh node 305 (a second terminal node) represents the destinationcomputing system (second terminal computing system). In this example,the initiating node 301 is depicted to be located in San Francisco ofthe United States. A user initiates a transfer from the initiatingcomputing system associated with the first node 301 using, for example,a client application 151 associated with the initiating computing systemof the first node 301. The transfer includes an indication of thedestination computing system associated with the seventh node 307 (e.g.,a routing number to the destination enterprise), an amount to betransferred, and/or an account number at the destination computingsystem that is to receive the amount of the transfer. However, asdepicted the destination may be located in India and in order for thetransfer to be completed, the funds associated with the transfer musttravel through the intermediary computing systems in order to reach theaccount at the destination computing system. In some embodiments, in theexample where the enterprise computing system 102 is not a participatingentity of the transfer, a computing system of the entity associated withthe first node 302 may map out all of the intermediary computing systems(e.g., and thereby the intermediary nodes 302-306) and transmit thatinformation to the enterprise computing system 102 to generate the firstvisualization layer. In the example where the enterprise computingsystem 102 is the initiating computing system associated with the firstnode 301, the enterprise computing system 102 may automaticallydetermine the nodes for the first visualization based on storedinformation regarding the route that a transfer must follow in order toreach the destination computing system (e.g., the seventh node 307).Once the enterprise computing system 102 has determined, based on theinitiating computing system and destination computing system in therequest, the intermediary computing system (e.g., the nodes 302-306)that the transfer will follow on its route from the initiating computingsystem (e.g., the first node 301) to the destination computing system(e.g., the seventh node 307), the enterprise computing system 102 thengenerates the first visualization layer based on the known (e.g.,cross-referenced) geographic location of the computing systemsassociated with each node 301-307.

Moreover, each of the nodes 301-307 have respective computing systems(e.g., intermediary computing systems 103 a-d) that the enterprisecomputing system 102 is able to identify based, for example, oninformation stored in the API database 125 regarding each of thecomputing systems. In this way, the enterprise computing system 102 isable to identify an API protocol in order to communicate with thecomputing systems associated with each of the nodes and retrieveinformation regarding the transfer. In some embodiments, the APIprotocol for each of the intermediary computing systems 103 a-d areunique. The enterprise computing system 102 can then ping or execute theAPI protocols by sending a request for information regarding thetransfer, and each of the intermediary computing systems 102 can sendback the information requested according to the respective API protocol.The first visualization layer 300 also includes various connectors 310(or other links or graphical indicators) between each of the nodes301-307 that indicate the route that the transfer is anticipated or hasoccurred. In some embodiments, the connectors 310 may also be used tovisually indicate the status of the transfer. For example, a solidconnector (e.g., a solid line or arrow) may be used between two nodes tovisually indicate to the user that the transfer has already taken placebetween the two connected nodes along the route. Continuing the example,a dashed connector (e.g., a non-solid line or arrow) may be used betweentwo or more nodes to visually indicate to a user that the transferbetween those two or more nodes has yet to occur. In this way, the firstvisualization layer may indicate to the user the current location of thetransfer without displaying additional information.

Referring now to FIG. 4 , an example of a rendered visualization 400including the first visualization layer and a second visualizationlayer, according to an exemplary embodiment. As an example, the renderedvisualization includes an overlay of the first visualization layer 300as depicted in reference to FIG. 3 with a second visualization layerincluding a graphical representation of a transfer status for each ofthe nodes 301-307. In particular, the second visualization layerincludes a first graphic 401 that indicates a first transfer status atthe first node 301, a second graphic 402 that indicates a secondtransfer status at the second node 302, a third graphic 403 thatindicates a third transfer status at the third node 303, a fourthgraphic 404 that indicates a fourth transfer status at the fourth node304, a fifth graphic 405 that indicates a fifth transfer status at thefifth node 305, a sixth graphic 406 that indicates a sixth transferstatus at the sixth node 306, and a seventh graphic 407 that indicates aseventh transfer status at the seventh node 307. Each of the transferstatuses were retrieved, for example, by executing an API protocol foreach of the nodes 301-307. The enterprise computing system 102 generatesthe graphics 401-407 using the information retrieved and overlays thegraphics 401-407 in a manner that indicates to a user that each of thegraphics 401-407 are associated with the respective node 301-307. Forexample, the first and second visualization layers are rendered andoverlaid in a configuration that places each graphic 401-407 near therespective node 301-307 such that a user can intuitively visualize thetransfer.

Moreover, the rendered visualization 400 may be interactive such that auser can selectively retrieve additional information regarding thetransfer. For example, the first node 301 and/or the first graphic 401may be selectable via a user input. Once selected, the renderedvisualization 400 may update to display more information regarding thetransfer at the computing system associated with the first node 301. Inthis example, once the first graphic 401 is selected, the renderedvisualization may zoom into the geographical area associated with thefirst node (e.g., California) and display a larger first graphic 401that includes additional information of the transfer at the first nodesuch as an agent at the first node 301 that is assigned to the transfer,a phone number or other contact information for the computing systemassociated with the first node, a date that the transfer was received, adate that the transfer was sent to the next node, an amount and currencyof the transfer received, and/or an amount and currency of the transferthat was sent to the next destination (e.g., the second node 302) alongthe route. Similarly, the other graphics 402-407 or nodes 302-307 mayalso be selectable to provide similar information to the user whenselected. In another example, the user, via an input to the user device101, may be able to zoom into or out of the visualization such that onlyparticular nodes 301-307 and respective graphics 401-407 of the renderedvisualization are displayed on the user device 101.

In some embodiments, the user device 101 includes one or more sensors117 that allow for user inputs via the user device 101. The one or moresensors 117 may include various cameras, detectors, light sources, andor other electronic equipment configured to capture one or more userinputs. In some embodiments, the one or more sensors 117 include an eyetracking system, a gesture or proximity sensing system, a depth sensingsystem, a touch screen, and/or a combination thereof. For example, auser input may include a user selection on a touch screen, a click froma mouse or keyboard, a verbal command received at a microphone, a handgesture determined by a camera, or an eye gesture determined by an eyetracking device of the user device 101. In an example of the user device101 include AR glasses, the rendered visualization may be displayed on adisplay as a hologram such that the user can see the surrounding areaand the rendered visualization 400. The AR glasses may include an eyetracking system comprising one or more light sources, detectors, and/orother optical devices. The AR glasses may also include one or moreoutward facing sensors such as cameras that are configured to sense anddetermine gestures such as hand gestures made by a user. The user mayinteract with the rendered visualization 400 by, for example, by verbalcommands, hand gestures, or eye gestures. An example of such interactionis described below in reference to FIG. 6 .

Referring now to FIG. 5 , a second example of a rendered visualization500 including the first visualization layer and a second visualizationlayer, according to an exemplary embodiment. The second example of therendered visualization 500 is similar to the rendered visualization 400described in reference to FIG. 4 . However, the second example of therendered visualization includes multiple transfers along the route ofthe nodes 301-307. It is to be appreciated that this is only one exampleof a rendered visualization that includes information regarding multipletransfers. For example, in other embodiments, it is contemplated thatmultiple transfers, each having a different route with multiple variousnodes or destinations associated with each may be rendered in variousembodiments.

The rendered visualization 500 includes a first visualization layer thatincludes the seven nodes 301-307 with a first connector 501, a secondconnector 502, and a third connector 503 therebetween. The firstconnector 501 is indicative a first transfer (e.g., transfer 1)initiated via a user device to a water company computing system in Indiahaving an account at the destination computing system (e.g., the seventhnode 307), the second connector 502 is indicative of a second transfer(e.g., transfer 2) initiated via a user device to a cleaning companycomputing system in India having an account at the destination computingsystem, and the third transfer (e.g., transfer 3) is indicative of athird transfer initiated via a user device to an electric companycomputing system having an account at the destination computing system.

The second visualization layer of the rendered visualization 500includes a status graphic 510 with the information for each transfer.For example, the status box 510 may include a name or identifier of therecipient for the first transfer (e.g., Water Co.), a transfer amount(e.g., $110), a status (e.g., completed), and/or a date associated withthe status. Moreover, the status box 510 may include a name oridentifier of the recipient for the second transfer (e.g., CleaningCo.), a transfer amount (e.g., $550), a status (e.g., Pending at thethird node 303), and/or a date indicating the last update. Additionallyor alternatively, the status box 510 may include a name or identifier ofthe recipient for the third transfer (e.g., Electric Co.), a transferamount (e.g., $180), a status (e.g., Pending at the fourth node 304),and/or a date indicating the last update. In various embodiments, thestatus box 510 may also include an estimated completion date and/or aprobability score that the transfer will be successful determined basedon historical information regarding similar transfers stored at theenterprise computing system. Moreover, in various embodiments, thesecond visualization layer of the rendered visualization 500 may alsoinclude one or more graphics for each of the transfers similar to thegraphics 401-407 described in reference to FIG. 4 .

Similar to the rendered visualization 400 as described in reference toFIG. 4 . The rendered visualization 500 may also be interactive orupdate based on one or more user inputs. For example, the renderedvisualization 500 may be displayed to a user and the user may issue avoice command of “Show me transfer 1.” In response to a microphone ofthe user device 101 receiving the voice command, the renderedvisualization 500 may update to show only information related to thefirst transfer. This updated rendered visualization may be similar tothe rendered visualization 400 of FIG. 4 . Further, the user device 101may receive or detect additional user inputs that update the display toshow more or less information based on the detected user input orgestures.

Referring now to FIG. 6 , depicts an updated visualization 600 updatedbased on a user input, according to an exemplary embodiment. Moreparticularly, the FIG. 6 depicts a user 601 interacting with thevisualization via the user device 101 (e.g., AR glasses 610) with avoice command 602 and a hand gesture 603. For example, a renderedvisualization such as the rendered visualization 400 or 500 wasdisplayed on a display of the AR glasses 610. The user 601 via a handgesture 603 detected by a gesture tracking system (e.g., includingoutward facing cameras) selected on a particular node (e.g., second node310), which caused the rendered visualization 600 to update and showmore particular information 620 about a transfer at the particular node.In this example, the more particular information includes the senderinformation, sending and receiving amounts and currencies, the receiversinformation, an agent associated with the transfer at the sendingentity, an agent associated with the transfer at the receiving entity,and information regarding a distributed ledger. In this example, theinformation regarding the distributed ledger includes a warning 650 thatthe hash number in the ledger was mutated and also includes informationregarding previous block information and/or a list of all of theentities that have been or will be involved with the transfer. In someembodiments, the intermediary computing systems may create a block hashusing similar methodologies to the one deployed by initiating computingsystem (e.g., using bank credentials of the user) in order to check thatthe original block (e.g., created by the initiating computing system andreceived by the intermediary computing system) was not mutated orchanged. This check may occur at each intermediary computing system andthe destination computing system, if one or more of the intermediarycomputing system or the destination computing system determine that ahash was mutated from its original form, that respective computingdevice may flag the transaction with the warning 650 and transmit thewarning 650 to the enterprise computing system 102 in response to theexecution of a respective API protocol. In some embodiments, theenterprise computing system 102 may generate a warning based on one ormore rules. In the example depicted, the enterprise computing system 102may compare the block information (e.g., the hash numbers in the ledger)received from a first node 301 (e.g., received in response to executingthe first API protocol) with the block information (e.g., the hashnumbers in the ledger) and issue a warning on the rendered visualizationif there is an unexpected value therein.

Further, the user 601 may issue a voice command 602 that is detected byone or more microphones of the AR glasses 610 that causes thevisualization to respond. For example, the user 601 in this exampleissues a voice command 602 of “show the distributed ledger technologyblock information.” In response to the voice command 602, the AR glasses606 and/or the enterprise computing system 102 may work together toupdate the visualization to display detailed information regarding theblocks of information associated with the distributed ledger such as thehash number or the previous block information that was used at the priornodes. In this way, at any moment, the user will be able to see the fulldistributed ledger technology with detailed block information includingthe hash number, previous block information from other users at theenterprise associated with the enterprise computing system 102, and/or alist of all of the entities or enterprises involved in the transfer.

As alluded to above, the enterprise computing system 102 may be used togenerate and provide a visualization of a multi-destination transfer inorder to make the transfer process as transparent as possible for theuser. In various examples, the multi-destination transfer includes anindustry standard international wire transfer. In other examples, themulti-destination transfer includes multi-destination transfers withcryptocurrencies or distributed ledgers. In the case of cryptocurrenciesand/or distributed ledgers, each computing system involved in thetransfer (e.g., transactional root) will create their own securedistributed ledger technology (DLT) block that is configured to bechecked with a DLT transaction block of the previous computing system.The created DLT block is a newly encrypted DLT block with informationregarding the previous DLT transaction block. For example, if a user 601is sending a transfer from San Francisco to London through anintermediary bank in New York, the transfer will include a firstencrypted DLT block created at the first computing system in SanFrancisco, a second encrypted DLT block created at the second computingsystem in New York, and a third encrypted DLT block at the thirdcomputing system in London. The various methods and systems describedherein allow for the enterprise computing system 102 to dynamicallyretrieve information regarding the first, second, and third DLT blocksin order to generate a rendered visualization to display to a user, thusmaking the process transparent and more secure. That is, for example,the exact information that is received, requested, accessed, orretrieved as part of the statuses of the transfer are dependent on thecontext and type of transfer that is being monitored. Accordingly, thesystems and methods described herein improve the ability of a computingsystem to monitor and track multi-destination transfers and also improvethe ability of the computing system to interact and provide informationto a user regarding transfers that would typically be obfuscated.

Referring now to FIG. 7 , depicts a flow diagram of a method 700 ofgenerating and updating a multi-nodal transfer, according to anexemplary embodiment. Because method 700 may be implemented using thecomponents of FIG. 1 , reference may be made to one or more componentsto aid explanation of method 700. Generally, method 700 relates tovarious processes implemented in order to provide a multi-layeredvisualization of a multi-node (e.g., multi-destination) transfer to auser.

At process 701, a transfer is initiated. As alluded to above, in someembodiments, the transfer may be initiated at a first computing systemand the system providing the visualization may be a separate enterprisecomputing system. Alternatively or additionally, in some embodiments,the transfer may be initiated at the first enterprise computing systemand the first enterprise computing system may also be involved in thetransfer. For example, the first enterprise computing system may be theenterprise computing system initiating the transfer or otherwise a partof the transfer process (e.g., a computing system associated one of thenodes). In the first example, where the first enterprise computingsystem is different from the system providing the visualization. Theenterprise computing system 102 may receive an indication and/or detailsof the transfer in response to a user enrolling (e.g., via a webinterface on the user device 101 or otherwise) as a user of servicesprovided by the enterprise computing system 102. For example, theenterprise computing system 102 may receive a form or application from auser device 101 in response to a user navigating to a web pageassociated with or provided by the enterprise computing system 102. Inresponse to approving the enrollment of the user, the enterprisecomputing system 102 may store profiling data (e.g., history oftransfers, current transfers, name, address, etc.) to a data instancefor the user within the user database 126. In various embodiments, theuser may enter information regarding particular transfers or enterprisesthat the user has initiated transfers with. For example, the user mayenter online login credentials for an entity that the user initiatestransfers with. In such an example, the enterprise computing system 102may establish an API session via executing an API protocol with acomputing system of the entity in order to retrieve data regardinginitiated transfers for the user (e.g., using the online logincredentials). The enterprise computing system 102 may then store, withinthe data instance associated with the user (e.g., user profile) in theuser database 126, the retrieved information. Alternatively oradditionally, the enterprise computing system 102 may receiveinformation regarding transfers directly from the user via a GUIpresented on the user device. In this example, the user device may beused to provide information such as a routing, an amount of transfer, aSociety for Worldwide Interbank Financial Telecommunications (SWIFT)code, an International Bank Account Number (IBAN) of the initiatingenterprise and/or destination enterprise, or other information that canbe leveraged by the enterprise computing system 102 to identify aparticular transfer and/or intermediary enterprises involved in thetransfer. In the example where the enterprise computing system 102 isassociated in the transfer, the enterprise computing system 102 may beable to retrieve information regarding transfers for a user by accessingthe user database 126 and analyzing the transaction history of the user.In some embodiments, the enterprise computing system 102 accesses,receives, (e.g., via an API call) or searches for (e.g., via analyzingthe user profile in the user database 126) the transfer information inresponse to a user request received from, for example, the user device101 at process 722. It is to be appreciated that the transferinformation accessed or retrieved at this process provides theenterprise computing system 102 with “seed transfer information.” Theseed transfer information is merely an indication that a transfer hasbeen initiated or that past transfers have occurred. The seed transferinformation may include some details received from the user or anothercomputing system associated with initiating the transfer that allows theenterprise computing system 102 to find and retrieve any remaining dataregarding the transfer from other entities involved in the transfer.However, additional information regarding the transfer beyond the seedtransfer information may be needed for the visualization.

At process 702, either in response to receiving or accessing the seedtransfer information (or, in response to a request received from theuser device 101 at process 722), additional data regarding the transferis orchestrated. For example, process 702 relates to various techniques,processes, and operations of the enterprise computing system 102 incollecting information regarding the transfer from each of the computingsystems involved in the transfer.

In various embodiments, the enterprise computing system 102 analyzes theseed transfer information to determine particular intermediary computingdevices 103 a-d that will be a part of the transfer. For example, theenterprise computing system 102 may cross-reference within a databasethe seed transfer information (e.g., initiating enterprise, destinationenterprise, type of transfer, etc.) to determine the intermediarycomputing devices 103 a-d that will be associated with the transfer.Alternatively or additionally, the enterprise computing system 102 mayrequest information regarding the identity of the intermediary computingsystems that will be involved in the transfer via an API call to a thirdparty computing system (e.g., a computing system of a regulator for theparticular type of transfer) or the initiating computing system. In someembodiments, the identity of each of the intermediary enterprises may bemanually entered, for example, by an agent or the user and the computingsystems associated therewith automatically identified.

Once the intermediary computing systems 103 a-d are identified, theenterprise computing system 102 retrieves contact information for eachof the intermediary computing systems. For example, the contactinformation may include an API protocol for each of the intermediarycomputing systems 103 a-d associated with the transfer. The contactinformation may be retrieved by the enterprise computing system 102, forexample, by cross-referencing each of the intermediary computing systemswithin the intermediary database 125. The enterprise computing system102 may use the contact information to request the information regardingthe transfer at each particular intermediary computing system. Theinformation regarding the transfer may be similar to the informationretrieved via the API sessions described above in reference to FIG. 2 .

In various embodiments, the enterprise computing system 102 is only ableto identify a first intermediary computing system 103 a. That is, theenterprise computing system 102 may communicate with the initiatingcomputing system (e.g., which, in some embodiments, may be theenterprise computing system 102 itself) to identify the firstintermediary computing system 103 a based on information of how thetransfer was initiated from the initiating computing system. In thisexample, the enterprise computing system 102 may communicate with thefirst intermediary computing system 103 a via an API call and requestdata regarding the transfer similar to as described above. In response,the enterprise computing system 102 receives requested the dataregarding the transfer along with an indication of the firstintermediary computing system 103 a will be making or has made thetransfer to. The enterprise computing system 103 a may continue tocommunicate with each subsequent intermediary computing system until thedestination computing system is reached.

At process 704, a decision whether an issue has been identified is made.If an issue is identified, the enterprise computing system 102 generatesand transmits a notification to, for example, the user device 101 tonotify the user or to a personal computing device associated with theenterprise computing system 102 to notify an agent at process 703. If noissue is identified, then the enterprise computing system proceeds toprocess 705. An issue may include a failure to identify one or moreintermediary computing systems 103 a-c, an indication in the informationregarding the transfer received from one or more of the intermediarycomputing systems 103 a-c that the transfer has stopped, stalled, orfailed, or a failure to identify an initiated transfer and/or seedtransfer information, and so on. The notification at process 703 mayinclude a text message, e-mail message, push notification, and/or a GUIthat contains textual information indicative of the identified issue.

At process 705, the data regarding the transfer from at least theinitiating computing system and one of the intermediary computingsystems 103 a is analyzed and augmented. For example, the enterprisecomputing system 102 performs one or more machine learning algorithmssimilar to as described above with the information regarding the data asinputs. In various examples, the enterprise computing system 102 mayestimate a completion time or date for the transfer based on a currentstatus determined from the transfer information and historicalinformation accessed from a database. Similar to as described above, theenterprise computing system 102 may determine an average amount of timethat each of the intermediary computing system have taken in previoustransfers to complete, determine the intermediary computing system thatthe transfer has yet to pass through, and sum the averages for each ofthe remaining intermediary computing system to estimate the completiontime or date for the transfer to complete. Moreover, the historicalinformation may be used to create other predictive models of thetransfer such as a probability of success, suggestions of times toperform the transfer, and/or other suggestions based on artificialintelligence algorithms using the historical information similar to asdescribed above.

In various embodiments, the enterprise computing system 102 may not havean API protocol that enables the enterprise computing system 102 tocommunicate with one or more of the intermediary computing systems 103a-d. In this example, the enterprise computing system 102 may determinebased on historical data and/or information accessed from one or moreother intermediary computing systems 103 b-c the statistical informationof the inaccessible intermediary computing system 103 a. In someembodiments, the statistical information may include information such asthe time that a particular historical transfer was received by theinaccessible intermediary computing system 103 a, when the transfer wasreceived by a successive intermediary computing system or destinationcomputing system, the times that transfers failed or never left theinaccessible intermediary computing system 103 a, and/or contextregarding each of the past transfers. The enterprise computing system102 may then model the inaccessible intermediary computing system 103 ain order to create a prediction for future transactions at theinaccessible intermediary computing system 103 a based on a calculatedaverage time that the inaccessible intermediary computing system 103 atakes to process the transfer, the probability of a successful transferat inaccessible intermediary computing system 103 a, and/or othercontextual information of the past transfers.

At process 706, a determination whether additional data regarding thetransfer is needed. For example, the enterprise computing system 102determines whether additional data for the machine learning algorithmsand/or the transfer are needed for the visualization. The additionaldata may include the need for contact information (e.g., telephonenumber, email, website, etc.) for an agent at one or more intermediarycomputing systems, additional details regarding the status of thetransfer being processed at an intermediary computing system, and/ordetails regarding the transfer such as a currency exchange rate (e.g.,if currency was exchanged at one or more of the intermediaryenterprises). For example, the status of the transfer received from oneof the intermediary computing system may be “pending.” The enterprisecomputing system 102 may determine that, based on historical averages,the transfer has been pending for an unusual amount of time (e.g., astandard deviation above the historical average). In response, theenterprise computing system 102 may determine that additional dataregarding the transfer and, in particular, the status of the transfer atthe one intermediary computing system. In response, the enterprisecomputing system 102 may proceed to process 702 to procure theadditional data. In this example, the enterprise computing system 102may transmit a request via an API call or by other methods such as anautomatically generated e-mail to the intermediary computing system 103requesting for an update regarding the status and prompt theintermediary computing system or user thereof to provide a responseindicative of whether there is an issue (e.g., “yes, there is an issue,”or “no, there is no issue”) and/or an indication of an estimated time ofcompletion.

At process 707, a determination of how to present the data regarding thetransfer is made. The enterprise computing system 102 may determine howto present the data regarding the transfer based on the context orapplication of the transfer. In various examples, the enterprisecomputing system 102 may present the data using a multi-layeredvisualization as described by various examples herein. For example, theenterprise computing system 102 may determine that the transfer is aninternational wire transfer and therefore a multi-layered visualizationcomprising a first visualization having multiple nodes positioned on ageographical map, one for each involved computing system, and a secondvisualization layer having transfer status graphical indicators shouldbe used. In another example, the enterprise computing system 102 maydetermine that the particular user making the request (e.g., at process722) has multiple transfers that need to be visualized. Accordingly,based on the data set for the multiple transfers, the enterprisecomputing system 102 may generate corresponding visualization layers toaccommodate the data set. For example, the second visualization layerand/or a third visualization layer may be generated if particular datafields in the data set are present.

At process 708, an interactive visualization is generated. Theenterprise computing system 102 then generates the interactivevisualization based on the determination of how to present the data. Forexample, the enterprise computing system 102 may generate theinteractive visualization using processes similar to as described inreference to method 200. As alluded to above, the data regarding thetransfer and/or data regarding multiple transfers within the userprofile may be rendered within the interactive visualization. As anexample, data regarding multiple transfers may each have a currentstatus (e.g., complete, pending at second intermediary enterprise,failed, etc.), an initiation date, a cost (e.g., fees), a paymentamount, a name of destination bank, and/or name of recipient (e.g., nameof person or company associated with the destination account at thedestination bank). The enterprise computing system 102 may generate theinteractive visualization to include a first layer having a geographicaldepiction of each intermediary enterprise, the initiating enterprise,and destination enterprise. The interactive visualization may alsoinclude a second layer having an indication or connector for each of themultiple transfers and associated initiation date, payment amount, andcost. Moreover, the interactive visualization may also include a thirdlayer including a graphical indicator of the names of the recipients andthe date at which the transfer was completed. In this way, theenterprise computing system 102 may render multiple visualization layersthat may be stacked and displayed to a user on a user device 102 inorder to provide most, all, or at least an indication of the acquireddata in a useful and interactive display.

At process 725, the interactive visualization is provided to the userdevice. In some embodiments, the enterprise computing system 102provides the interactive visualization to the user device 101 via thenetwork 106. The user device 101 then displays the received interactivevisualization to a user. In some embodiments, as alluded to above, thedisplay may be a touchscreen, an AR or VR display on an eye ware device,and/or another type of monitor or display. The user device 101 may thenmonitor for user inputs and a determination of whether a user input isdetected is made at process 709. In some embodiments, the user input mayinclude a voice command (e.g., detected via a microphone on the userdevice 101), a click from a mouse or keyboard, a physical gesturedetected from an eye tracking system or a gesture tracking system,and/or other type of user input. In response to detecting the userinput, the user device 101 may transmit an indication of the user inputto the enterprise computing system 102 and/or otherwise respond. If nouser input is detected, then the interactive visualization may continueto be displayed and/or updated in pre-determined time periods. Inresponse to receiving the indication of the detected user input, theenterprise computing system 102 may determine if additional informationis needed to be retrieved at process 706. For example, the user inputmay include a voice command of “show me the first transfer statusinformation at enterprise X.” If available, the enterprise computingsystem 102 may update the interactive visualization to include the firsttransfer status information at enterprise X at process 710. If theinformation is not available, the enterprise computing system 102 hasdetermined that additional information is needed and proceeds to process702 to retrieve the first transfer status information at a computingsystem of enterprise X. If the information cannot be retrieved, theissue is reported via a notification to the user device 101, forexample, at process 703.

Referring now to FIG. 8 , depicts a multi-layered visualization 800 fora user, according to an exemplary embodiment. The multi-layeredvisualization 800 may be one example of the interactive visualizationgenerated at process 708. In this example, the multi-layeredvisualization includes three visualization layers having stacked data. Afirst visualization layer includes a geographical map 829 having a firstnode 820, a second node 821, a third node 822, a fourth node 823, and afifth node 824, each of the nodes corresponding to an enterpriseinvolved in one or more transfers and geographically positioned on themap in a geographic position associated with a respective enterprise. Inthis example, each of the nodes are depicted using a three dimensionalgraphical indicator.

The second layer includes information regarding one or more transfers.In this example, the one or more transfers include a first connector 840associated with a first transfer, a second connector 841 associated witha second transfer, a third connector 842 associated with a thirdtransfer, and fourth connector 843 associated with a fourth transfer. Inthis example, the enterprise computer system 102, responsive to arequest received from a user interface, determined that the fourtransfers were associated with the user and thus should be included inthe visualization 800. In this example, each connector 840, 841, 842,and 843 includes an indication of a payment amount 890, an indication ofthe transfer date 891.

The third layer includes information for one or more of the nodesrelating generally to the transfers and/or information determined by theenterprise computing system 102 that is a priority to depict to theuser. For example, the third layer includes a first graphical indicator830 depicting the agents at the first node 820 (e.g., the initiatingenterprise) that were involved with one or more of the transfers, asecond graphical indicator 831 indicating savings information at thesecond node 821 (e.g., a first intermediary enterprise), and a thirdgraphical indicator 832 indicating context of the transfer. In thisexample, a user located in San Francisco may own a flat or rentalproperty in Indonesia. The user may access their account from theenterprise computing system 102 requesting to view the transfersassociated with payments for the flat or rental property. The enterprisecomputing system 102 may then access or retrieve information for eachpayment, generate the visualization 800, and cause the visualization 800to display on the user device 101 similar to as described above. Thethird graphical indicator 832 includes a visual of the flat or rentalproperty and information regarding each of the identified transfersassociated with the flat. In this example, the third graphical indicator832 includes a warning 807 within the third graphical indicator 832 thatindicates to the user that a transfer associated with the cleaning fees(e.g., the fourth transfer 843) for the flat have not been transferredand/or received yet. That is, the enterprise computing system 102 hasidentified an issue with the transfer associated with the cleaning fees(e.g., the fourth transfer 843) and has issued a notification to warnthe user that the transfer has not been completed. The other transfers(e.g., first, second, and third transfers) are displayed without awarning thereby indicating to the user that no issues have beenidentified with respect to them. In this example, the user may issue avoice command (e.g., user input) to see the information regarding thefourth transfer 843. Responsive to the voice command, the enterprisecomputing system 102 may determine the information available orotherwise retrieve additional data regarding the fourth transfer 843from the various nodes associated with the fourth transfer 843 andupdate the display to show the status and geographic position of thefourth transfer 843 along with any retrievable indications of why thetransfer has been delayed or otherwise failed. For example, thevisualization may be updated to only display the step-by-step processestaken with respect to the fourth transfer 843 at each node and/or anindication that the fourth transfer 843 is at the third node 822 and theexpected processing date at the third node 822. In other examples,additional or alternative data may be retrieved based on the context ofthe transfer and the nodes involved. Similar to as described above, auser input may select any of the connectors, transfers, graphicalindicators, and/or nodes. Responsive to the user input, the enterprisecomputing system 102 may proceed with processes 709, 706, and 710 inorder to dynamically retrieve information requested from the respectivecomputing systems associated with one or more of the transfers.

Moreover, a user input may indicate to the enterprise computing system102 and/or user device 101 that the user wishes to call one of theagents at the first node 811. In this example, the user input may be aneye gesture toward the first graphical indicator 830 and/or one of theagents. Responsive to detecting the eye gesture, the user device 101 mayrequest contact information for the agent and/or first node 820 from theenterprise computing system 102, which may retrieve and transmit backthe contact information. In some embodiments, the user device 101 mayautomatically call or otherwise contact the agent using the receivedinformation. Another user input may indicate to the enterprise computingsystem 102 that the user wishes to see additional information associatedwith the second graphical indicator 831. In this example, the user inputmay be a click or selection of the second graphical indicator 831.Responsive to the user input, the enterprise computing system 102 maydetermine whether additional information regarding why the user saved$15 is needed. In some embodiments, the enterprise computing system 102implements one or more machine learning algorithms to update thevisualization with an explanation of why the user saved $15 (e.g., “Yousaved $15 by transferring the water payment in January. January isassociated with better exchange rates and less fees.”). It is to beappreciated that these example are not meant to be limited andadditional information may be determined to be needed based on thecontext of the transfers and/or user inputs.

Referring now to FIG. 9 , depicts multiple visualizations 900 as avisualization is updated with additional information over time,according to an exemplary embodiment. For example, FIG. 9 includes afirst visualization 910 at a first time, a second visualization 950 at asecond time, and a third visualization 975. The first, second, and thirdvisualizations 910, 950, and 975 show, for example, how the interactivevisualization may be updated at subsequent times based on newlyretrieved or received information. In this example, the first, second,and third visualizations 910, 950 and 975 relate to a block chain ordistributed ledger technology (DLT) transfers. The first, second, andthird visualizations 910, 950 and 975 include first layer having ageographical map and multiple nodes, each node corresponding to arespective enterprise, and a second layer including one or moregraphical indicators representative of a status of the transfer at arespective node. For example, the first visualization 910 includes afirst graphical indicator 901 depicting a message that a first node issending a signed transaction at the first time. The second visualization950 includes a multiple graphical indicators such as a first graphicalindicator 902 depicting the status of the transfer at the first node asvalidated. In this example, validated may indicate to the user that theDLT information has been checked and validated similar to the validationprocesses described above. A second graphical indicator 903 may depict amessage that a fifth node has failed to validate the DLT. That is, thedistributed ledger at the fifth node may include a hash that has beenmodified. This may prompt a user to issue a user input and thereby causethe enterprise computing system 102 to retrieve additional dataregarding the distributed ledger from the fifth node along with anyinformation related to why the distributed ledger could not be validatedand display that information to the user in an updated visualization(e.g., similar to the updated visualization described in reference toFIG. 6 ).

The third visualization 975 includes a first graphical indicator 905that indicates to the user that the enterprise computing system 102 isin the process of updating the status of the respective node. Forexample, the visualization may, in some embodiments, be dynamicallyupdated and/or displayed before all of the information regarding thetransfer is compiled. The third visualization 975 may also include asecond graphical indicator 907 for the destination node (e.g.,destination enterprise) indicating that the transaction using the DLThas been completed. In this way, the user is able to visualize andinteract with the many enterprises associated with a transfer via thevisualization provided by the enterprise computing system 102.

It is noted that any element in a visualization may be selectable toallow the user to obtain additional information about the selectedelement. To aid interactions, visualizations may allow switching betweensets of elements (e.g., layers) through, for example, a Layer Toggleelement 899 shown in FIG. 8 . In various embodiments, different layersmay include or be associated with different information. For example, afirst layer may represent geographical or physical elements, a secondlayer may represent a first transfer with a first time stamp, and thirdlayer may represent a second transfer with a second time stamp). Layersmay vary on interactivity in addition to graphical elements and visualrepresentations, such that, for example, one layer may be rotatablewhile another layer may be zoomed or panned.

Various potential embodiments of the approach disclosed herein will nowbe presented:

Various embodiments may relate to a method comprising generating a firstvisualization layer comprising a set of geographic or physicaldestinations in a route, the set of destinations comprising a firstnode, a second node, and a third node, identifying a first computingapplication program interface (API) protocol corresponding with thefirst node, and a second API protocol corresponding with the secondnode, executing the first API protocol to obtain, from a first computingsystem, a first status of a transfer and executing the second APIprotocol to obtain, from a second computing system, a second status ofthe transfer, generating a second visualization layer comprising a firstgraphic corresponding with the first status and a second graphiccorresponding with a second status, and displaying an overlay of thefirst visualization layer with the second visualization layer such thatat least two nodes in the set of destinations are displayed inassociation with the first and second graphics.

Generating the first visualization layer may comprise determining theset of geographic or physical destinations in the route based oninformation regarding the transfer including an initiating enterpriseand a destination enterprise.

Identifying the first API protocol may comprise identifying a firstcomputing system associated with the first node and cross-referencingthe first computing system within an API database.

Identifying the second API protocol may comprise identifying a secondcomputing system associated with the second node and cross-referencingthe first computing system within the API database.

Executing the first API protocol may comprise generating a request tothe first computing system for the first status, the first statuscomprising an amount and currency of the transfer received and an amountand currency of the transfer sent.

The method may further comprise: receiving a user input, the user inputcomprising a selection of the first node; and in response to the userinput, updating the display to include information regarding an entityassociated with the first node, the information regarding the entitycomprising contact information for the entity and an agent associatedwith the transfer at the entity.

The method may further comprise: accessing historical transferinformation for one or more of the nodes; estimating a completion dateof the transfer based on the historical information of the one or morenodes; and augmenting the overlay to include a graphical indication ofthe estimated time.

The method may further comprise: accessing historical transferinformation for one or more of the nodes; and determining a probabilityscore indicative of the likelihood that the transfer is completed basedon the historical transfer information of the one or more nodes.

The overlay may be displayed on augmented reality (AR) glassescomprising an eye tracking system, a microphone, and a gesture capturesystem, the gesture capture system configured to enable a user of the ARglasses to cause the display to interactively update based on one ormore captured gestures.

The method may further comprise: receiving a user input indicative of atoggle between the first visualization layer and the secondvisualization layer; and responsive to the user input, displaying onlythe first visualization layer or the second visualization layer.

The method may further comprise: identifying a third computing APIprotocol corresponding with the third node; and executing the third APIprotocol to obtain, from a third computing system, a third status;wherein the second visualization layer comprises a third graphiccorresponding to the third status.

The method may further comprise: accessing a third status correspondingto the third node from memory; wherein the second visualization layercomprises a third graphic corresponding to the third status.

Various embodiments relate to a non-transitory computer readable mediaincluding instructions stored thereon. The instructions, when executedby one or more processors configured to cause the operations includinggenerating a first visualization layer comprising a set of geographic orphysical destinations in a route, the set of destinations comprising afirst node, a second node, and a third node, identifying a firstcomputing application program interface (API) protocol correspondingwith the first node, and a second API protocol corresponding with thesecond node, executing the first API protocol to obtain, from a firstcomputing system, a first status of a transfer and executing the secondAPI protocol to obtain, from a second computing system, a second statusof the transfer, generating a second visualization layer comprising afirst graphic corresponding with the first status and a second graphiccorresponding with a second status, and providing a graphical userinterface (GUI) comprising an overlay of the first visualization layerwith the second visualization layer such that at least two nodes in theset of destinations are displayed in association with the first andsecond graphics.

The non-transitory computer readable media may comprise instructionsthat, when executed by one or more processors, cause the operations of:generating a first visualization layer comprising a set of geographic orphysical destinations in a route, the set of destinations comprising afirst node, a second node, and a third node; identifying a firstcomputing application program interface (API) protocol correspondingwith the first node, and a second API protocol corresponding with thesecond node; executing the first API protocol to obtain, from a firstcomputing system, a first status of a transfer and executing the secondAPI protocol to obtain, from a second computing system, a second statusof the transfer; generating a second visualization layer comprising afirst graphic corresponding with the first status and a second graphiccorresponding with a second status; and providing a graphical userinterface (GUI) comprising an overlay of the first visualization layerwith the second visualization layer such that at least two nodes in theset of destinations are displayed in association with the first andsecond graphics.

Generating the first visualization layer may comprise the operations ofdetermining the set of geographic or physical destinations in the routebased on information regarding the transfer including an initiatingenterprise and a destination enterprise.

The non-transitory computer readable media may comprise instructionsconfigured to cause the operations of: generating a third visualizationlayer comprising a first graphical indicator including an indication ofmultiple related transfers; and displaying the third visualization layeroverlaid on the first visualization layer and the second visualizationlayer.

The GUI may be provided to augmented reality (AR) glasses via a network.

The non-transitory computer readable media may comprise instructionsconfigured to cause the operations of: in response to receiving a usergesture captured by the AR glasses, updating the GUI to displayadditional information associated with the user gesture.

Various embodiments may relate to a system including a processor and amemory storing instructions thereon. The instructions, when executed bythe processor, cause operations including generate a first visualizationlayer comprising a set of geographic or physical destinations in aroute, the set of destinations comprising a first node, a second node,and a third node, identify a first computing application programinterface (API) protocol corresponding with the first node, and a secondAPI protocol corresponding with the second node, execute the first APIprotocol to obtain, from a first computing system, a first status of atransfer and executing the second API protocol to obtain, from a secondcomputing system, a second status of the transfer, generate a secondvisualization layer comprising a first graphic corresponding with thefirst status and a second graphic corresponding with a second status,and provide a graphical user interface (GUI) comprising an overlay ofthe first visualization layer with the second visualization layer suchthat at least two nodes in the set of destinations are displayed inassociation with the first and second graphics.

The system may further comprise instructions that, when executed by theprocessor, cause the operations including identify a third computing APIassociated with the third node.

The system of may further comprise instructions that, when executed bythe processor, cause the operation including, execute the third API toobtain a third status of the transfer from a third computing system.

The system may further comprise instructions that, when executed by theprocessor, cause the operation including, obtain information regarding asecond transfer, the second transfer comprising a fourth node, a fifthnode, and a sixth node along a second route; and update the firstvisualization to include the fourth node, the fifth node, and the sixthnode.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that implement the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” or “computing system” may includehardware structured to execute the associated functions describedherein. In some embodiments, each respective “circuit” or “computingsystem” may include machine-readable media for configuring the hardwareto execute the associated functions described herein. The “circuit” or“computing system” may be embodied as one or more circuitry componentsincluding, but not limited to, processing circuitry, network interfaces,peripheral devices, input devices, output devices, sensors, etc. In someembodiments, a circuit may take the form of one or more analog circuits,electronic circuits (e.g., integrated circuits (IC), discrete circuits,system on a chip (SOCs) circuits, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” In this regard, the“circuit” or “computing system” may include any type of component foraccomplishing or facilitating achievement of the associated operationsdescribed herein. For example, a circuit as described herein may includeone or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR,NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors,inductors, diodes, wiring, and so on).

The “circuit” or “computing system” may also include one or moreprocessors communicatively coupled to one or more memory or memorydevices. In this regard, the one or more processors may executeinstructions stored in the memory or may execute instructions otherwiseaccessible to the one or more processors. The one or more processors maybe constructed in a manner sufficient to perform at least the associatedoperations described herein. In some embodiments, the one or moreprocessors may be shared by multiple circuits (e.g., circuit A andcircuit B may comprise or otherwise share the same processor which, insome example embodiments, may execute instructions stored, or otherwiseaccessed, via different areas of memory). Alternatively or additionally,the one or more processors may be structured to perform or otherwiseexecute certain operations independent of one or more co-processors. Inother example embodiments, two or more processors may be coupled via abus to enable independent, parallel, pipelined, or multi-threadedinstruction execution. Each processor may be implemented as one or moreprocessors, application specific integrated circuits (ASICs), fieldprogrammable gate arrays (FPGAs), digital signal processors (DSPs), orother suitable electronic data processing components structured toexecute instructions provided by memory. The one or more processors maytake the form of a single core processor, multi-core processor (e.g., adual core processor, triple core processor, quad core processor, etc.),microprocessor, etc. In some embodiments, the one or more processors maybe external to the apparatus, for example the one or more processors maybe a remote processor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem, etc.) or remotely (e.g., as part of a remote server such as acloud based server). To that end, a “circuit” or “computing system” asdescribed herein may include components that are distributed across oneor more locations.

An exemplary system for implementing the overall system or portions ofthe embodiments might include a computer(s), including a processingunit, a system memory, and a system bus that couples various systemcomponents including the system memory to the processing unit. Eachmemory device may include non-transient volatile storage media,non-volatile storage media, non-transitory storage media (e.g., one ormore volatile and/or non-volatile memories), etc. In some embodiments,the non-volatile media may take the form of ROM, flash memory (e.g.,flash memory such as NAND, 3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM,magnetic storage, hard discs, optical discs, etc. In other embodiments,the volatile storage media may take the form of RAM, TRAM, ZRAM, etc.Combinations of the above are also included within the scope ofmachine-readable media. In this regard, machine-executable instructionscomprise, for example, instructions and data which cause a generalpurpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.Each respective memory device may be operable to maintain or otherwisestore information relating to the operations performed by one or moreassociated circuits, including processor instructions and related data(e.g., database components, object code components, script components,etc.), in accordance with the example embodiments described herein.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed is:
 1. A computer-implemented method comprising:generating a first visualization layer comprising a set of geographic orphysical indicators in a multi-nodal transfer route, the transfer routecomprising a set of three or more nodes that include terminal nodes andat least one transitional node, wherein the geographic or physicalindicators correspond to locations of computing systems that are alongthe transfer route and that implement transfers between nodes in the setof nodes of the transfer route; identifying a first computingapplication program interface (API) protocol corresponding to a firstnode in the transfer route, and a second API protocol corresponding to asecond node in the transfer route; executing the first API protocol toobtain, from a first computing system, a first data packet correspondingto the first node, and executing the second API protocol to obtain, froma second computing system, a second data packet corresponding to thesecond node; generating a second visualization layer comprising, basedon at least one of the first data packet and the second data packet, afirst graphic visually depicting a first detail of a transfer of an itemalong the transfer route and a second graphic visually depicting asecond detail of the transfer of the item along the transfer route; anddisplaying an overlay of the first visualization layer with the secondvisualization layer such that the first graphic and the second graphicare displayed in association with at least two nodes in the set ofnodes.
 2. The method of claim 1, wherein generating the firstvisualization layer comprises identifying, via the first computingsystem or the second computing system, the set of geographic or physicalindicators in the multi-nodal transfer route.
 3. The method of claim 1,wherein generating the first visualization comprises rendering ageographic model of the transfer route.
 4. The method of claim 3,further comprising displaying a first graphical indicator that links thefirst detail to a first geographic location in the first visualization,and a second graphical indicator that links the second detail to asecond geographic location in the first visualization.
 5. The method ofclaim 1, further comprising visually stacking data by displaying (i) afirst stack indicating a first transfer from the first node to thesecond at a first time, and (ii) a second stack indicating a secondtransfer from the first node to the second node at a second time.
 6. Themethod of claim 1, wherein the second visualization layer corresponds toa first transfer along the transfer route with a first time stamp, andwherein the method further comprises generating a third visualizationlayer corresponding to a second transfer along the transfer route with asecond time stamp.
 7. The method of claim 6, further comprisingdisplaying a graphical layer toggle enabling selection of whichvisualization layer is currently controllable such that a user mayinteract with graphical elements associated with a selectedvisualization layer.
 8. The method of claim 7, further comprisingincreasing a visibility of the selected visualization layer relative toanother visualization layer.
 9. The method of claim 1, wherein the firstand second nodes are transitional nodes.
 10. The method of claim 1,further comprising: receiving a user input indicating a selection of oneof the nodes; and in response to receiving the user input, updating thedisplayed overlay to include additional information regarding theselected node.
 11. The method of claim 1, further comprising applying amachine-learning model to transfer data to generate a prediction of afuture transfer detail, and augmenting the displayed overlay with agraphical depiction of the prediction.
 12. The method of claim 1,further comprising: accessing historical transfer information for one ormore of the nodes; and determining a likelihood that the transfer iscompleted based on the historical transfer information for the one ormore nodes.
 13. The method of claim 1, wherein the overlay is displayedon augmented reality (AR) glasses configured to enable a user of the ARglasses to cause the display to interactively update based on one ormore captured gestures.
 14. The method of claim 1, further comprisingcapturing a gesture corresponding to selection of one of the nodes inthe transfer route, and augmenting the overlay with additionalinformation related to the selected node.
 15. A computer-implementedmethod comprising: generating a first visualization layer comprising aset of geographic or physical indicators in a multi-nodal transfer routecomprising a set of three or more nodes that include terminal nodes andat least one transitional node; identifying a first computingapplication program interface (API) protocol corresponding to a firstnode in the transfer route, and a second API protocol corresponding to asecond node in the transfer route, wherein identifying the first APIprotocol comprises identifying, in an API database, a first APIcorresponding to the first computing system and determining a firstspecification for the first API, and identifying the second API protocolcomprises identifying, in the API database, a second API correspondingto the second computing system and determining a second specificationfor the second API; executing the first API protocol to obtain, from afirst computing system, a first data packet corresponding to the firstnode, and executing the second API protocol to obtain, from a secondcomputing system, a second data packet corresponding to the second node;generating a second visualization layer comprising, based on at leastone of the first data packet and the second data packet, a first graphicvisually depicting a first detail of a transfer of an item along thetransfer route and, (ii) based on the second data packet, a secondgraphic visually depicting a second detail of the transfer of the itemalong the transfer route; and displaying an overlay of the firstvisualization layer with the second visualization layer such that thefirst graphic and the second graphic are displayed in association withat least two nodes in the set of nodes.
 16. The method of claim 15,wherein: executing the first API protocol comprises generating a firstAPI request according to the first specification, and executing thefirst API to transmit the first API request to the first computingsystem; and executing the second API protocol comprises generating asecond API request according to the second specification, and executingthe second API to transmit the second API request to the secondcomputing system.
 17. The method of claim 16, wherein the first datapacket is generated and transmitted by the first computing system inresponse to receiving the first API request, and wherein the second datapacket is generated and transmitted by the second computing system inresponse to receiving the second API request.
 18. The method of claim 17wherein the first data packet comprises first time and locationinformation for an item received or detected by the first computingsystem along the transfer route, and wherein the second data packetcomprises second time and location information for the item received ordetected by the first computing system along the transfer route.
 19. Asystem comprising one or more processors configured to: generate a firstvisualization layer comprising a set of geographic or physicalindicators in a route comprising a set of nodes that includes a firstnode, a second node, and a third node, wherein the geographic orphysical indicators correspond to locations of computing systems thatare along the route and that are involved in transfers between nodes inthe set of nodes of the route; identify a first application programinterface (API) protocol corresponding to the first node, and a secondAPI protocol corresponding to the second node; execute the first APIprotocol to obtain, from a first computing system, a first status of atransfer and execute the second API protocol to obtain, from a secondcomputing system, a second status of the transfer; generate a secondvisualization layer comprising a first graphic corresponding with thefirst status and a second graphic corresponding with a second status;and provide a graphical user interface (GUI) comprising an overlay ofthe first visualization layer with the second visualization layer suchthat at least two nodes in the set of nodes are displayed in associationwith the first and second graphics.
 20. The system of claim 19, furtherconfigured to capture a gesture corresponding to selection of one of thenodes in the transfer route, and augmenting the overlay with additionalinformation related to the selected node.